chore(deps): update dependency stackexchange.redis to 3.0.7#6307
Conversation
thomhurst
added
dependencies
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Dependency update review: StackExchange.Redis 3.0.0 → 3.0.7
This is a Renovate-generated patch bump that correctly updates StackExchange.Redis in two independent locations. The 3.0.7 release brings bug fixes (unobserved task exceptions on connection teardown) and a memory optimization (MemoryPool buffering) — no breaking changes.
Why two files need updating
I verified the package management structure before signing off on this:
- Root
Directory.Packages.props— governs the main TUnit project tree viaManagePackageVersionsCentrally=true. This controls the version used byTUnit.Example.Asp.Net(and any other main-tree consumers). examples/CloudShop/CloudShop.Tests/CloudShop.Tests.csproj— CloudShop has its ownexamples/CloudShop/Directory.Packages.propsthat setsManagePackageVersionsCentrally=false, opting the entire CloudShop sub-solution out of CPM. Projects in that scope must carry explicitVersionattributes, so the csproj update is genuinely needed and independent.
Renovate found both pin locations correctly.
No issues found
The dual-pin pattern is intentional and architecturally sound given the CPM opt-out. The changes are minimal and low-risk for a patch release. Nothing to action here.
✅ LGTM — safe to merge.
Dependency update review: StackExchange.Redis 3.0.0 → 3.0.7This is a Renovate-generated patch bump that correctly updates StackExchange.Redis in two independent locations. The 3.0.7 release brings bug fixes (unobserved task exceptions on connection teardown) and a memory optimization (MemoryPool buffering) — no breaking changes. Why two files need updatingI verified the package management structure before signing off:
Renovate correctly identified both pin locations. No issues foundThe dual-pin pattern is intentional and architecturally sound given the CPM opt-out. The changes are minimal and low-risk for a patch release. ✅ LGTM — safe to merge. |
2 participants
This PR contains the following updates:
3.0.0→3.0.7Release Notes
StackExchange/StackExchange.Redis (StackExchange.Redis)
v3.0.7Compare Source
What's Changed
MemoryPool<byte>sources for request/response buffering by @mgravell in #3107ConfigurationOptions.RequestBufferPoolandConfigurationOptions.ResponseBufferPoolFull Changelog: StackExchange/StackExchange.Redis@3.0.0_main...3.0.7
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.